Rapid application integration

ABSTRACT

Techniques are provided to integrate two or more application systems by using an declarative approach that describes functions or rules to be performed to integrate application systems. Particular integration functions are defined that may be useful for common integration activities. Integration functions may be defined for particular objects and may be assembled to form a declarative business process flow. The declarative business process flow identifies the objects to be exchanged between two or more systems, the sequence of particular transformation functions, the physical field to field transformations required, and the physical connection to be established between the systems. An application integration workstation is described that provides a framework and tools to design, develop and modify (or maintain) application integration software. Such an application integration workstation may reduce the time required to construct or maintain application integration software, which may be referred to as “rapid application integration.”

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority from U.S. Provisional Application No.60/406,637, filed Aug. 29, 2002, and titled “Rapid ApplicationIntegration,” U.S. Provisional Application No. 60/406,643, filed Aug.29, 2002, and titled “Rapid Application Integration Using FunctionalAtoms,” and from U.S. Provisional Application No. 60/406,631, filed Aug.29, 2002, and titled “Isolated Mapping Point,” all of which areincorporated by reference.

TECHNICAL FIELD

This description relates to techniques for exchanging data between twoor more computer systems.

BACKGROUND

A database, such as a relational database, an object-oriented database,or another type of data management system, may be used for theadministration of data processed by a computer system running one ormore application programs or systems. Examples of application programsor systems include an enterprise resource management system, a customerrelationship management system, a human resources management system, asupply chain management system, and a financial management system. Datafrom one data management system used for one application system may needto be sent to one or more data management systems for storage and use byother application systems. The transfer of data from one data managementsystem to another data management system may be referred to as a dataexchange. When two data management systems or application systems needto exchange data on a routine basis, the development of a data exchangecapability may be referred to as the integration of the applicationsystems.

The development of data exchange capabilities between two applicationsystems may involve the design, coding and testing of software designedfor exchanging data between the particular data management systems. Suchsoftware may be referred to as application integration software.Application integration software may be developed through manual designand programming of the software with little or no use of design andprogramming tools. Manually designing and programming software forintegrating application systems may be an impractical method tointegrate disparate application systems, particularly when a number ofdisparate application systems must be integrated or application systemsmust be integrated rapidly.

An alternative to manually designing and programming applicationintegration software is to use a code generation program, such as a CASE(“computer-aided software engineering” or “computer-aided systemsengineering”) tool, to integrate application systems. In general, CASEtools may provide automated support for the process of designing andprogramming software (for example, producing source code and/orexecutable instructions). CASE tools may employ a visual designinterface that permits a user to diagram the procedural and dataelements required and how the elements are related to or used in thesoftware.

One type of automated support for computer system integration is agraphical user interface that may be used for creating a specificationfor data management system integration. The specification describes aworkflow that relates a series of executable communication scripts anddata translators that are used to integrate two computer systems. Anexecutable communication script may be based on a generalization of aparticular interactive session that establishes a connection between thetwo computer systems and exchanges data between two data managementsystems. A data translator identifies the data fields to be sent fromone system to the other system and a translation rule for each datafield. An example translation rule may be to delete trailing blanks atthe end of a data value of a particular data field before sending thedata value to the other system.

SUMMARY

Techniques are provided to integrate two or more application systems byusing a declarative approach to application integration. Applicationintegration refers to the connection of two or more systems through dataexchange. Application integration may occur, for example, when a newsystem is installed, a new version of system installed, or a system withwhich the application communicates is changed. Application integrationmay represent a significant portion of the cost of owning and operatingan application system (which may be referred to as the total cost ofownership). The reduction of the time needed to design and implementapplication integration software needed to translate data from onesystem and/or data format to another system and/or data format mayimprove application integration.

Application integration may use a declarative approach to integration.In general, a declarative approach describes the functions or rules tobe performed to produce a result. In contrast, a procedural approachspecifies the explicit sequence of steps to follow to produce a result.A declarative approach for application integration uses reusablepatterns to declare the rules used and the functions performed inapplication integration software.

A reusable pattern may be a functional atom that represents a unit ofintegration that is performed either completely or not at all inapplication integration software. Examples of reusable patterns that arefunctional atoms include data processing functions, such as thetransformation of data according to a set of transformation rules,separating data from a single document, segment, or record intodifferent documents, segments, or records, joining data from more thanone document, segment or record to a single document, segment or record.Additional functional atoms include reading from and writing to a datastore, initiating a particular process, or applying a set of validatingrules to a data set.

A reusable pattern also may be a collection of functional atoms. One ormore functional atoms may be collected, for example, in a library ofintegration functions. A reusable pattern accessible from a library (orother type of collection or group) of integration functions may bereferred to as an integration design pattern.

One or more functional atoms also may be collected to form a mapscenario that represents an integration function to be performed by theapplication integration software. A map scenario may include one or moreother map scenarios. Through the use of a stack approach of including(or nesting) one or more map scenarios within another map scenario, theintegration functions to be performed be the application integrationsoftware may be represented.

Reusable patterns (such as one or more functional atoms, integrationdesign patterns, or map scenarios) may be defined for integrationfunctions that commonly occur when integrating two application systems.For example, a map scenario may be defined for the bulk transfer of databetween two systems, error checking associated with received data, ordata transformation functions, such as transforming data identifiersfrom a proprietary identifier format to a global unique identifierformat.

An application integration workstation may leverage a declarativeapproach to integration by providing a framework and tools to design,develop and modify (or maintain) application integration software. Theapplication integration workstation may be an integrated developmentenvironment (IDE) that tightly couples a visual tool for declaring rulesand functions for the integration application software with the reusablepatterns, such as a functional atom or integration design pattern, usedin the integration application software. For example, a particularelement displayed by the visual tool may be associated with one or morereusable patterns and/or a particular portion of application integrationsoftware. A user of the application integration workstation may displaythe reusable patterns (or portion of application integration software)associated with a displayed element in the visual tool by selecting thedisplayed element or may display the displayed element in the visualtool associated with a reusable pattern (or portion of applicationintegration software) by selecting the reusable pattern (or portion ofapplication integration software).

The use of a declarative approach may reduce the time required toconstruct or maintain application integration software, which may bereferred to as “rapid application integration.” For example, the timerequired to construct or maintain application integration software maybe reduced when the functions performed by the application integrationsoftware are made more visible to the application integration softwaredeveloper through the use of reusable patterns. A developer may be ableto better comprehend the functions performed by the applicationintegration software when reusable patterns are used. The reusablepatterns may provide one or more additional layers of abstraction thataid the developer's comprehension.

Application integration also may use an isolated mapping point that is acomputer system, a server, or other computing device that includes amapping database and performs mapping functions. An isolated mappingpoint receives data from the sending system, transforms the data asnecessary, and sends the transformed data to the receiving system. Theisolated mapping point performs the data transformation withoutaccessing data or processes on the sending system or the receivingsystem. The isolated mapping point is separate (or isolated) from boththe sending system and the receiving system. The isolated mapping pointuses only data included in the mapping database or received through awell-defined interface (for example, data sent in, or along with, amapping request from the sending system).

By including a mapping database, the isolated mapping point may avoidthe need to access any application-specific data for performing the datatranslations (and hence the name isolated mapping point). The isolatedmapping point also may be referred to as an isolated mapping pointbecause the isolated mapping point replaces the use of invisible,undocumented interfaces for data translations and isolates the datatranslation (or mapping) from one system to another system in the singleaccess point.

The isolated mapping point also may be used to provide a common documentobject that is a data model of data used by different applicationprograms in a standard format. By communicating using the commondocument object, the number of interfaces that need to be developed toexchange data in a network of computer systems may be reduced.

Through the use of an isolated mapping point, the integration ofapplication systems may be decoupled (or separated) from the technicalmethods of communication and the application systems being integrated.This may improve the ability to substitute one application system withanother application system in a heterogeneous landscape of applicationsystems that need to be integrated. For example, an application systemthat has been previously integrated with another application system mayhave to be replaced. When the application integration software does notuse the application system to be replaced to provide the transformationrules or data for any data transformation needed in the integration, theapplication system may be more quickly and easily replaced because theapplication system may be replaced without developing transformationrules or new data access programs that previously had been performed bythe application system to be replaced.

An isolated mapping point may be developed using conventional proceduralintegration programming or other conventional software engineeringtechniques. For example, application integration software may bedeveloped without the use of CASE tools or other code generation tools.

Alternatively, an isolated mapping point may be developed using adeclarative approach. The benefits of rapid application integration(such as the greatest reduction of cost associated with integratingapplications and/or a substantial reduction in the amount of timerequired to integrate applications) may be increased when both adeclarative approach and an isolated mapping point are used to integrateapplication systems. For example, an isolated mapping point may use adeclarative approach that increases the efficiency of the isolatedmapping point.

To fully understand the techniques presented in this description, thechallenges and issues of application integration need to be fullyunderstood. Data management systems, such as a relational database, anobject-oriented database, or another type of data management system, arewidely used for administration of data which are processing byapplication programs or systems running on computer systems. In arelational database, the data form a large number of two-dimensionaltables, which describe a relationship. A table may, for example, relateto an object and to data which can be uniquely associated with theobject. For example, the customer data of a company may be stored in a“customer” table whose columns relate to different customer attributes(for example, company name, billing address, contact information). Thevalues for different customers form the rows in the table. The tablescontained in relational databases relate not only to objects but also torelationships between objects. For example, when an order for a specificcustomer is processed, the “order” table that is generated for theadministration of orders contains a “for customer” attribute that isused to define the customer-order relationship (for example, identifiesthe customer to which the order applies). Such attributes (which may beimplemented by the use of pointers from one object to another in thedatabase) play a major role for representing relationships betweenobjects that are described by different tables in a database.

Data stored by different data management systems may use different datamodels that require data to be transformed (or converted or translated)to a different data structure before the data can be accepted or used bythe other system. To accomplish data exchange between two heterogeneousdata management systems, data structures in a data management system maybe mapped onto one another. In addition, the data contents need to bematched appropriately (for example, the object “customer” in one systemcorresponds to “buyer” in another system). For example, one datamanagement system may store data values representing a particularattribute using a different field type and length as that used by adifferent data management system. A data management system may usedifferent data codes than another data management system. For example,one system may store a country value using a numeric code (for example,a “1” for the United States and a “2” for the United Kingdom) whereasanother system may store a country value as a textual abbreviation (forexample, “U.S.” for the United States and “U.K.” for the UnitedKingdom). The country codes in the two systems may be identified asrepresenting the same attribute and then a translation table madeavailable that translates the various possible values from one system toanother system (for example, “1” to “U.S.” and “2” to “U.K.”).

Data stored by different data management systems also may use differentprimary key structures to uniquely identify a particular data object.For example, one system may use a proprietary key numbering system inwhich primary keys are created by sequentially allocating numbers withinan allocated number range. Another system may use a GUID (“globallyunique identifier” or “global unified identifier”) key that may becreated based on a combination of a few unique settings based onspecific point in time (for example, an Internet Protocol address, adevice MAC (Media Access Control) address, and clock date and time). Inorder to accurately exchange data, the key values may need to be mappedfrom one system to another system.

Data stored by different data management systems also may use differentdata management system types. For example, data may be stored by arelational database in one system and stored as an XML (“ExtensibleMark-up Language”) document in another system. XML is a language similarto hypertext markup language (HTML) but with the additional flexibilityof being able to describe data structures that can be processed directlyas data by a program. The data formats used to exchange data need to usea format that is able to be used by the receiving data managementsystem.

These data mapping complexities complicate the data exchange betweensystems that need to be integrated. Often data mapping transformationsare accomplished using application-specific code that may be hidden fromthe data transformation interface. When the application-specific code ismodified, the data exchange program that uses the application-specificcode may malfunction.

Data exchange also may be complicated by the number of different systemswith which a particular system needs to be integrated. Often data mayneed to be exchanged with a network of interconnected computer systems,some of which may be owned and operated by the same corporate entity andsome of which may be owned and operated by different legal entities. Forexample, a customer relationship management system used for enteringcustomer orders may need to be integrated with an order processingsystem used to process each entered order, a financial management systemused for financial reporting, and multiple suppliers with whom one ormore orders are placed. Each supplier typically is a different corporateentity than the company that places the order.

In addition, data exchange software may need to be modified when any oneof the systems is modified or replaced. For example, a supplier or otherbusiness partner may be changed and data exchange software may have tobe developed for the new supplier or other business partner. Often dataexchange software may need to be developed under strict timeconstraints, such as when a supplier is replaced with a new supplier.The time and costs associated with developing and maintaining dataexchange software may be a significant portion of the total cost ofownership of a particular application program or system.

Data exchange also may be complicated when data enhancement (orenrichment) needs to occur when data is exchanged with another system.For example, application systems that operate on portable computingdevices (such as a personal digital assistant or laptop computer) mayhave fewer data fields than corresponding data fields on another systemthat receives data from the application system on the portable computingdevice. Data may not be accepted by the other system without adding datafields that are required by the receiving application system. Forexample, the application system on the portable computing device may notinclude data fields that are mandatory on the receiving applicationsystem. For data to be accepted by the receiving application system, themandatory data must be entered, for example, by adding default datavalues that are added or adding data values applicable to the particularrecord.

In one general aspect, a system is used to design, develop or modifyapplication integration software that performs data exchange between atleast two application systems. The system may be used to design, developor modify a declarative integration workflow. A declarative integrationworkflow may identify data to be exchanged. The data may include atleast one type of data. The data may include at least one datacollection. A data collection may be an object, an object type, anobject instance, a database table, a database segment, a database tablerow, a document capable of being accessed thorough a format that may betransmitted by an Internet Protocol, an XML-document, a text file, abinary file, or a message.

A declarative integration workflow may represent two or more applicationsystems between which data is to be exchanged. A declarative integrationworkflow may represent at least two application services between whichdata is to be exchanged. Each service may be associated with anapplication system.

The declarative integration workflow may represent at least oneintegration design patterns that describe a data exchange between atleast two application services. The declarative integration workflow mayrepresent at least one integration design pattern that describes afunction included in a particular data exchange between at least twoapplication systems. An integration design pattern may include a patternfor validating a data collection for mandatory information, a patternfor splitting data from one data collection into separate datacollections, a pattern for invoking a key mapping function, a patternfor invoking a data transformation function, a pattern for invoking aconnectivity function for a particular application system, or a patternfor invoking a connectivity function for invoking a particular service.An integration design pattern may decompose into two or more integrationdesign patterns. The declarative integration workflow may indicate asequence order of at least two integration design patterns.

The system may be used to generate application integration softwarebased on a declarative integration workflow. The generated software maybe a template for application integration software, source code, and/orexecutable software instructions. The generated software may also bemodifiable by a user after it has been generated. In addition, thesystem may associate the generated application integration software witha declarative integration workflow. For example, the system mayassociate at least one portion of the generated software with at leastone portion of a declarative integration workflow, with each particularportion of the application integration software being associated with aparticular portion of the declarative integration workflow.

The system may be used to generate application integration softwarebased on a layer of application integration. Application integrationlayers may include a business process layer, an integration designpattern layer, a functional atom layer, a data transformation rulelayer, a data layer, and a physical connection layer. The system layermay identify at least one application system or computing system withwhich a data exchange or other application integration function is to beperformed. The service layer may identify at least one service on acomputing system. The integration design pattern layer may identify orinclude at least one declarative design pattern that identifies anintegration function that may be leveraged during a data exchange orother application integration function. The functional atom layer mayidentify at least one functional atom that declaratively describes adiscrete action that relates to an application integration function. Thedata transformation rule layer may identify or include a datatransformation rule or other data transformation logic that describeshow data may be changed or transformed. The data layer may identify orinclude data, such as object instances, attributes, attribute values,and control data, that may be included in an application integrationfunction. The physical connection layer may identify or include aphysical connection and network that is used to connect two computersystems involved in an application integration function.

Another aspect is a design workstation and accompanying user interfacethat is used to design, develop or modify a declarative integrationworkflow. The design workstation may generate the user interface used todesign, develop or modify a declarative integration workflow. The designworkstation may include some or all of the features previouslydescribed.

Implementations of the techniques discussed above may include a methodor process, an apparatus or system, or computer software on acomputer-accessible medium. The details of one or more of theimplementations are set forth in the accompanying drawings anddescription below. Other features will be apparent from the descriptionand drawings, and from the claims.

DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of a network of systems that exchange data usingapplication integration software developed using an applicationintegration workstation.

FIG. 2 is a diagram illustrating the results of data transformsperformed by application integration software designed, developed andmaintained by an application integration workstation.

FIG. 3 is flow chart for an example process to develop applicationintegration software using an application integration workstation.

FIG. 4 is a flow chart for an example process to modify applicationintegration software using an application integration workstation.

FIGS. 5-7 are diagrams of functional atoms of application integrationsoftware.

FIG. 8 is a diagram of a multi-layer architecture for applicationintegration software.

FIG. 9 is a diagram of the components of a software architecture for anapplication integration workstation.

FIG. 10 is a diagram of the components of a software architecture for anapplication integration software or program that includes functionalatoms.

FIG. 11 is a diagram of a process used to transform customerrelationship management system data using functional atoms.

FIG. 12 is a example of an XML representation of a map scenario.

FIGS. 13-16 are examples of XML representations of functional atoms.

FIGS. 17-18 are diagrams of example user interfaces for an applicationintegration workstation.

FIG. 19 is a diagram of functional atoms that may be generated by anapplication integration workstation that generates the interface of FIG.18.

FIGS. 20-21 are diagrams of the components of software architectures forapplication integration software that exchanges data with a groupwaresystem.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION

FIG. 1 shows a network of systems 100 in which a computer system 110exchanges data with computer systems 115, 120, and 125. The computersystem 110 uses application integration software 112 to direct the dataexchange with computer systems 115, 120, and 125. An applicationintegration workstation 130 is used to develop and maintain theapplication integration software 112. The computer system 110 is capableof delivering and exchanging data with computer system 115 throughcommunication gateway 135. The computer system 110 is capable ofdelivering and exchanging data with computer systems 120 and 125 throughcommunication gateway 138. As is conventional, each computer system 110,115, 120 or 125 includes a server 140, 142, 144, or 146 and a datastorage device 150, 152, 154, or 156 associated with each server. Datastorage device 150 includes data 158 and executable instructions 159 forthe application integration software 112 on computer system 110. Each ofthe data storage devices 152, 154, and 156 includes data 162, 164, or166 and executable instructions 172, 174, or 176 for data exchangesoftware and/or one or more application systems on computer system 115,120, or 125.

The application integration workstation 130 provides automated supportto a user in the design, development (or construction) and maintenanceof the application integration software 112 on computer system 110. Thecomputer system 110 and application integration workstation 130 may bearranged to operate within or in concert with one or more other systems,such as, for example, one or more LANs (“Local Area Networks”) and/orone or more WANs (“Wide Area Networks”). The application integrationworkstation 130 may be a general-purpose computer that is capable ofoperating as application integration workstation (for example, a desktoppersonal computer, a workstation, or a laptop computer running anapplication program), or a more special-purpose computer (for example, adevice specifically programmed to operate as an application integrationworkstation).

The application system on computer system 115, in this example, is anorder processing application that receives orders entered through amobile client 185 that connects to computer system 115 through gateway190. The mobile client 185 may be a general-purpose computer, such as alaptop, a special-purpose computer, or another mobile computing device,such as a personal digital assistant (“PDA”) or a portable personalcommunicator. A mobile client 185 provides a user of the mobile clientwith functions and data to enter orders placed by customers. The mobileclient 185 stores the executable instructions and data used by themobile client user.

Communication gateways 135, 140 and 190 may each connect mobile client185 or computer systems 110, 115, 120, or 125 to the Internet, the WorldWide Web (web), WANs, LANs, analog or digital wired and wirelesstelephone networks, satellite, and/or any other delivery mechanism forcarrying data. Communication gateways 135, 140 and 190 may connectthrough, for example, a wired, wireless, cable, or satellitecommunication pathway.

Computer system 115 sends order data to computer system 110 throughcommunication gateway 135. The computer system 110 uses applicationintegration software 112 to translate the received order data into asupplier order data message that is sent to computer system 120. Thesupplier order data sent to computer system 120 is the data in theformat required by a supplier order processing application system oncomputer 120. Similarly, computer system 110 uses applicationintegration software 112 to translate the received order data into asecond supplier order data message that is sent to computer system 125.The supplier order data sent to computer system 120 is the data in theformat required by a supplier order processing application system oncomputer 125.

The computer system 110 distributes the messages using communicationgateway 138 to the supplier order processing application systemoperating on computer system 120 and the supplier order processingapplication system operating on computer system 125. The orders then areavailable for processing by the supplier applications operating oncomputer systems 120 and 125.

FIG. 2 illustrates the results 200 of data transformations performed byapplication integration software designed, developed, and maintained byan application integration workstation. The application integrationsoftware may be, for example, the application integration software 112in FIG. 1 developed using application integration workstation 130 inFIG. 1.

Order data 210 represents customer order data as entered by a user andstored as a customer order in a customer order processing system. Forexample, order data 210 may have been entered by a user of mobile client185 in FIG. 1 and stored on computer system 115. Order data 210 includesdata values for customer number, customer name, customer country, ordernumber, order date, and products ordered. The products includes a datavalue for the quantity ordered for product number. The products orderedalso includes a data value for the quantity ordered for product number.

Order data 215 represents order data as transformed by the applicationintegration software. The order data 215 includes values (though notnecessarily the same values) as the order data fields in order data 210.The application integration software that received order data 210transformed particular data values based on executable instructions anddata included in the application software. The received order number wastransformed to a different value as shown by order data. The applicationintegration software may have used a key mapping function to translatethe key value order number to a different representation used by orderdata 215. The format of order date in order data 210 is transformed to adifferent representation as shown by order date in order data 215. Forexample, application integration software may have used a date formattranslation to transform the order date into order date. The value forcustomer country in order 215 was modified from the customer countryvalue in order 210. For example, a customer country data translationtable may have been used to translate the text value “U.K.” used inorder data 210 to the numeric value “2” used in order data 215.

The application integration software replicated order data 215 andmodified each copy of order data 215 to create order data 220 or 225.Order data 220 was modified to include the appropriate data in a formatusable by a first supplier from whom one of the ordered products ispurchased. Order data 225 was modified to include the appropriate datain a format usable by a second supplier from whom the second orderedproduct is purchased. Order data 220 is sent to the first supplier.Order data 225 is sent to the second supplier. Specifically, theapplication integration software produces order data 220 that includesonly the data necessary to place an order with a first supplier for oneproduct in order data 210. Order data 225 contains only the datanecessary to place an order with a second supplier for the other productin order data 210.

FIG. 3 depicts a process 300 for developing application integrationsoftware using an application integration workstation. In general, adeveloper identifies two application systems involved in exchanging dataand a connection between the two application systems that represents thedata to be exchanged. For the connection, the developer identifies aseries of declarative integration design patterns to describe the dataexchange (including data transformation) between the applicationsystems. The developer may identify a declarative integration workflowthat identifies the objects to be exchanged between two or more systems,the sequence of particular transformation functions, the physical fieldto field transformations required, and the physical connection to beestablished between the systems. A declarative integration designpattern is a reusable pattern that declares the rules used and thefunctions performed to integrate the two application systems. Functional(or integration) atoms that represent a unit of integration that iseither performed completely or not at all in the integration are thengenerated by the application integration workstation. The functionalatoms may be assembled into source code and/or executable instructionsfor application integration software.

The application integration software developed in FIG. 3 may be referredto as a business process flow. The server that executes the businessprocess flow may be referred to as a business process server. A businessprocess flow may include more than one map scenario. Typically, abusiness process flow includes many map scenarios. A map scenario isexecuted by a mapbox that is a service, or other group of executablefunctions, in a server environment. For example, a mapbox used toexecute a map scenario may be embedded in a web server environment or adata processing server environment that includes remote procedure callsand/or remote function calls. The application integration software maybe used to perform the data exchange between the application systems.Additionally, in some implementations, the developer may identify morethan two application systems to be integrated. The developer iterativelydescribes each service connection. The application integrationworkstation generates application integration software for each serviceconnection. In some implementations, data exchange may occur for morethan two application systems.

More specifically, the process 300 begins when a developer selects oneor more systems from a list of systems presented by the applicationintegration workstation (step 310). For each system selected, thedeveloper identifies one or more services from a list of possibleservices (for example, web services) available from that system whichare presented by the application integration workstation (step 320). Theapplication integration workstation presents both the list ofapplication systems and the list of web services available from eachsystem by accessing a component landscape repository (that storesapplication systems and services available from each applicationsystem). The developer selects the services with which to work. Forexample, the developer may select one or more components from apresented list and the application integration workstation may deletethe services that are not selected. Alternatively, the developer maydelete one or more presented services such that the undeleted servicesindicate which components are selected.

The developer then defines a declarative integration workflow for theservices identified in step 320 (step 330). A declarative integrationworkflow may identify a series of declarative patterns that accomplishthe data exchange between the identified services. A declarative patternmay identify a reusable component for an integration function, such as acomponent that identifies the data to be exchanged, the datatransformations to be performed, and data validation to be performed.The declarative patterns, for example, may include an integration designpattern (described below in step 340) or a functional atom (describedbelow in step 350). A declarative integration workflow is defineddeclaratively through the identification and sequencing of reusablecomponents. In contrast, a conventional approach to the development ofapplication integration software may merely identify the data to beexchanged between two different application systems.

For example, to start the definition of a declarative integrationworkflow, the developer may connect two services with a line indicatingthat the services exchange data with one another. Each line represents aservice connection (or an application integration step) for whichintegration information must be defined and for which applicationintegration software must be developed. The developer may continue todefine additional service connections until all of the serviceconnections have been identified for a declarative integration workflow.

The developer then proceeds to select a particular service connectionfor which the connectivity and data transformation is declarativelydefined (step 335). For the selected service connection, the developeridentifies and connects integration design patterns (step 340). Forexample, the developer may be presented with a series of control shapes(or a palette) in a window. Each control shape may be associated with aparticular integration design pattern. The developer may drag-and-drop aparticular control shape from the palette onto a second window. Thedeveloper may order or otherwise sequence the control shapes in thesecond window. Example integration design patterns include validating anobject for mandatory information, splitting data from one object intoseparate objects, invoking a key mapping function (for example, callinga subroutine that translates a key field for customer information in oneapplication system to a key field for the same customer information inanother application system), invoking a data transformation function,and invoking a connectivity function for a particular web-service. Somedesign patterns may decompose into additional patterns. For example,invoking a particular key mapping function may call an additional designpattern to identify the values in the key field, read the key valuestore to identify the corresponding key in the target data, generate anew key if needed, and update the output document with theaccessed/generated key.

The application integration workstation then generates a map scenariofor the particular service connection (step 350). The applicationintegration workstation generates a map scenario that includes one ormore functional atoms based on the integration design patternsidentified and connected in step 340. For example, the applicationintegration workstation may access a table that identifies a predefinedmap scenario and/or one or more functional atoms to be generated basedon each integration design pattern identified. The map scenariogenerated may include XML documents with an XML document correspondingto a functional atom. The XML documents may be combined into a singlemap scenario XML document.

In some cases, a map scenario or a functional atom template may begenerated and the template may be modified by a developer. For example,a functional atom may include a generic template for connecting to anapplication system. In this example, the generic template may includeselecting a particular communication mode (for example, a synchronousmode or an asynchronous mode), identifying one or more queues with whichto be connected, and providing system authentication information (forexample, a user or account name or password). In some implementations, adeveloper may select a particular functional atom that includes theconnectivity information required for a particular web service. In sucha case, the developer may select a particular connectivity functionalatom and does not need to modify a connectivity functional atom thatincludes only a connectivity template.

Optionally, the developer may modify the map scenario or map scenariotemplate generated (step 360). For example, the developer may select anintegration design pattern, and the application integration workstationmay present a list of functional atoms that correspond to the selectedintegration design pattern. The developer then may select a particularfunctional atom to modify. The application integration workstationdisplays the functional atom. The developer may edit the functional atomand save the modified functional atom. In some cases, when only onefunctional atom corresponds to the integration design pattern selected,the application integration workstation may display the functional atomwithout first presenting a list of the one functional atom from whichthe developer selects the only functional atom presented.

The application integration workstation stores the map scenario (step365). The map scenario may be stored in a map store or other type ofdata repository.

The developer determines whether another service connection needs to bedefined (step 370). If so, the developer selects a particular serviceconnection (step 335) and proceeds as described previously. When thedeveloper has completed the definition of the service connections, theapplication integration workstation stores the business process flow(step 390). The business process flow includes a map scenario for eachservice connection. The business process flow also may includeconnection parameters to establish a connection with service connectionsincluded in the business process flow. The business process flow may bestored in repository. The application integration workstation may storeother information about the integration landscape associated with thebusiness process flow. For example, a list of the application systems,the services, the declarative integration workflow, and functional atomsthat correspond to each integration design pattern in the declarativeintegration workflow may be associated with the business process flowand stored

The design and development of application integration software using adeclarative process, such as process 300 in FIG. 3, may be beneficial.For example, the application integration software generated isstructured based on functional atoms. The structured applicationintegration software generated may be more comprehensible to developersand may result in fewer programming errors.

Referring to FIG. 4, a business process flow may be modified using avisual modeling interface. In general, the application integrationworkstation presents a visual representation of the integrationlandscape defined for a particular business process flow. The businessprocess flow may include one or more service connections, and eachservice connection may be associated with a map scenario. The visualrepresentation may be similar to the one described in FIGS. 17-19. Theapplication integration landscape may have been defined, for example,using a process the same as or similar to process 300 in FIG. 3. Adeveloper identifies a portion of the landscape to be modified (forexample, an application system, a service, a service connection, a mapscenario, an integration design pattern in a service connection, or afunctional atom associated with a design pattern in a serviceconnection). The application integration workstation presents theportion of the map scenario that corresponds to the portion of thelandscape identified.

The use of a visual modeling interface or process in the modification ofapplication integration software, such as a map scenario, may bebeneficial. For example, the developer identifies the portion of theapplication integration software to be modified using a model. Thedeveloper may not need to search through many and/or voluminous sourcecode modules to find the portion of the application integration softwareto be modified as the developer otherwise may have had to do. Thedeveloper also may be reminded by features in the integration landscapepresented that additional modifications may need to be made that thedeveloper otherwise may not have realized.

FIG. 4 depicts an example process 400 for modifying applicationintegration software that uses declarative design patterns to integrateapplications. In example process 400 a particular service connection ina business process flow is modified by replacing one or more integrationdesign pattern in the service connection and/or modifying one or morefunctional atoms. The developer identifies a particular business processflow to modify (step 410). For example, a list of all business processflows in a repository may be presented from which the developer selects.Alternatively, the developer may be able to identify a particularbusiness process flow by name, key identifier, or other uniqueidentifier.

The application integration workstation presents an integrationlandscape that is associated with the business process flow (step 415).The integration landscape may have been defined and stored, for example,using a process the same as or similar to process 300 in FIG. 3. Theintegration landscape includes one or more application systems, at leastone service for each application system, and one or more serviceconnections that indicate a data exchange between two services. Theintegration landscape also includes a declarative integration workflowfor each service connection. The declarative integration workflowincludes one or more integration design patterns and the flow (or orderof invoking) each integration design pattern. The integration landscapeincludes a list of the one or more functional atoms associated with eachintegration design pattern in the declarative integration workflow.

The developer identifies a particular service connection to modify (step420). The application integration workstation presents the map scenariothat is associated with the identified service connection (step 425).The presentation of the map scenario includes the presentation ofintegration design patterns for a service connection that are associatedwith the map scenario. When the developer determines that an integrationdesign pattern in the identified service connection is to be replacedwith a different integration design pattern (step 430), the developerselects a new particular integration design pattern to replace theexisting one (step 435). For example, the developer may identify aparticular integration design pattern based on a unique identifierassociated with the particular integration design pattern. The developermay identify a particular integration design pattern by selecting one(for example, by double-clicking a pointing device while a particularintegration design pattern is identified) from several integrationdesign patterns presented. The developer identifies an integrationdesign pattern to add, such as by selecting an integration designpattern from several integration design patterns presented (step 440).This may be accomplished in a manner the same as or similar to step 340in FIG. 3. The developer may identify an integration design pattern byidentifying a particular integration design pattern using a name orunique identifier. The developer adds one or more connections from theadded integration design pattern to other integration design patterns inthe map scenario (step 445). The application integration workstationgenerates one or more functional atoms for the added integration designpattern (step 450). This may be accomplished, for example, in a mannersimilar to step 350 in FIG. 3. Optionally, the functional atoms in themap scenario may be modified by the developer, as described in step 360in FIG. 3.

When a developer determines that a functional atom is to be modified andso indicates to the application integration workstation (step 455), theapplication integration workstation presents a list of integrationdesign patterns associated with the service connection identified instep 420 (step 460). For each integration design pattern presented, theapplication integration workstation identifies the one or morefunctional atoms associated with the integration design pattern. Forexample, the application integration workstation may present a list ofintegration design patterns, with the functional atoms associated witheach integration design pattern presented as a list nested under theassociated integration design pattern.

The developer identifies a particular functional atom to modify (step465), and the application integration workstation presents the portionof the map scenario that relates to the functional atom identified (step467). The developer may review and modify the displayed functional atom(step 470). The developer may continue to review and make modificationsto a service connection by replacing an integration design pattern(steps 435-450) and by modifying a functional atom (steps 460-470) untilthe developer is satisfied.

After the developer has completed modifying the business process flow,the application integration workstation may store the modified businessprocess flow (step 475). The application integration workstation storesthe modified business process flow only when one or more functionalatoms have been modified or when one or more integration design patternshave been replaced.

The process 400 is an example of how a business process flow may bemodified. Some implementations may use other processes and softwareengineering techniques to modify a business process flow or an aspect ofa business process flow. For example, a service connection may be addedto the integration landscape of a particular business process flow. Theapplication integration workstation may present the integrationlandscape and the developer may add a new service connection, forexample, as described in steps 335-360 in FIG. 3, to a business processflow associated with the integration landscape. The functional atomsgenerated may be added to a map scenario associated with the businessprocess flow.

In some implementations, a developer may identify a particular serviceconnection to be deleted. For example, a developer may use a pointingdevice to identify a particular service connection (for example, clickon the service connection) to be deleted (for example, the developer maydrag-and-drop the service connection into a delete container). Theapplication integration workstation may remove from the business processflow the functional atoms in the map scenario associated with theservice connection from the business process flow. The applicationintegration workstation may use the integration landscape information todetermine which functional atoms are associated only with the serviceconnection. For example, the application integration workstation maystore a direct association between a functional atom and a serviceconnection. Additionally or alternatively, the application integrationworkstation may determine the association between a functional atom anda service connection indirectly. For instance, the applicationintegration workstation may determine which declarative integrationworkflow is associated with the service connection, determine whichintegration design patterns are associated with the associateddeclarative integration workflow, and determine which functional atomsare associated with each integration design pattern associated with theassociated declarative integration workflow. The application integrationworkstation may delete each identified functional atoms when aparticular functional atom is only used in the service connection to bedeleted. For example, the application integration software generated bythe application integration workstation may permit a functional atom tobe used in only one service connection.

Alternatively or additionally, a developer may identify a particularservice to be deleted. The application integration workstation removesall functional atoms in the map scenario related to the all of theservice connections that involve the identified service. Similarly, adeveloper may identify a particular system for which all services are tobe removed. The application integration workstation removes from the mapscenario each functional atom associated with an integration designpattern that is associated with a service connection that is associatedwith the particular system that is to be removed.

In some cases, an application integration workstation may permit adeveloper to add one or more services for a system in the integrationlandscape of the business process flow. An application integrationworkstation may permit a developer to add to the integration landscapeone or more systems and one or more services associated with each addedsystem.

Referring to FIGS. 5-7, types of functional atoms are illustrated. Ingeneral, a functional atom declaratively describes a type of discreteintegration procedure. The functional atom includes data transformationlogic. A functional atom defines the semantic processing necessary toperform a particular data transformation process. Functional atoms maybe implemented, for example, as a program module, a subroutine, or aseries of XML documents. For example, the contents of an XML documentmay be transformed using the eXtensible stylesheet Language (“XSL”) andthe XSL Transformation language (XSLT). In general, an XML processor mayapply data transformation rules stored in an XSLT stylesheet to an XMLdocument to create a transformed XML document.

FIGS. 5-7 respectively illustrate data processing atoms 500, datapersistency atoms 600, and helper atoms 700. The functional atoms shownin FIGS. 5-7 are provided as illustrative implementations. Someimplementations may use other types of functional atoms. One or morefunctional atoms may be used in application integration software usedfor data exchange. One or more functional atoms may be grouped in a mapscenario. A mapbox is a service that executes a map scenario.

FIG. 5 shows illustrative data processing atoms 500, including atransform atom 510, a branch atom 520, an unbranch atom 530, a splitatom 540, and a join atom 550. The transform atom 510 receives an XMLdocument as input (here, document T) and a transformation rule. Thetransformation rule may be an XSLT stylesheet that contains one or moretransformations. The XSLT stylesheet also may include some programmaticcode (such as code developed in the Java programming language) that maybe executed out of the stylesheet. The mapbox processor applies theidentified XSLT stylesheet to the received XML document to produce thetransformed XML document. All data required by the transform atom 510 isprovided through the XML document received or the map scenario. Thetransform atom 510 is not permitted to access any external data. Thetransform atom 510 produces a transformed XML document (here, documentT′). The XML document received as input or produced as output by thetransform atom 510 or any other atoms may be represented, for example,as an XML-Document Object Model (DOM) document that is a parsedrepresentation of an XML document in memory using a tree structure. DOMis a specification that describes how objects in a Web page arerepresented.

The branch atom 520 divides the received XML document into one or moreseparate XML documents. The branch atom 520 allows conditionalprocessing to be performed on the transformed XML documents. The branchatom 520 receives an XML document (here, document B), transforms thereceived XML document into various XML documents based on the contentwithin the received XML document, and produces one or more transformedXML documents (here, document B1 and document B2). Typically, more thanone transformed XML document is produced by a branch atom 520. Thetransformed documents then may be processed differently using subsequentatoms based on the content contained in the transformed documents. Thebranch atom 520 identifies each output XML document as a sequentialnumber of a total number (for example, 1 of 4, 2 of 4, 3 of 4, 4 of 4)in a particular map scenario process.

The functional counterpart to a branch atom 520 is an unbranch atom 530.The unbranch atom 530 receives a set of one or more XML documents (here,documents B1 and B2) and begins processing the XML documents only whenall of the input documents have been received. The unbranch atom 530determines when all of the input documents have been received based onthe total number of documents as identified by the branch atom thatproduced the input document. This may enable the unbranch atom 530 todetermine how many input documents are required when the unbranch atom530 receives any one of the input documents. The unbranch atom 530 doesnot require that the documents be received in sequential order. Theoutput document produced by the branch atom 520 may be an XML document.The output XML document includes all data from the one or more input XMLdocuments. Here, the output document produced is document U.

Like the branch atom 520, the split atom 540 accepts a single XMLdocument as its input (here, document S) and produces a set of one ormore XML documents (here, document S1 and document S2). Typically, asplit atom 540 produces more than one XML document. The split atom 540divides the received XML document based on the identification ofrepeated data of a similar kind (for example, an array) within thereceived XML document. Each output XML document includes a sequentialtag that identifies the sequential number of the document produced andthe total number of XML documents produced, as does the branch atom 520.The split atom 540 may facilitate parallel processing. Each XML documentproduced may be processed independently in a separate processing path(or thread) from the other XML documents produced by split atom 520.This may enable a map scenario to take advantage of parallel processingcapability in a computing system.

The join atom 550 accepts a set of one or more XML documents (here,document S1 and document S2) that were produced by a split atom. Thejoin atom 550 waits for all of the required XML documents to beginprocessing. Like the unbranch atom 530, the join atom 550 determineswhether all required XML documents have been received based on thesequential tag associated with any of the received input XML documents.

FIG. 6 illustrates data persistency atoms 600 including a write atom 610and a read atom 620. The write atom 610 provides the capability to themap scenario to store a particular XML document in storage accessible tothe mapbox. For example, the write atom 610 may store an XML documentusing a particular key value in a map scenario repository, such as mapscenario repository 970 of FIG. 9 or map store 1030 of FIG. 10. Thewrite atom 610 accepts one or more key values and data stored in an XMLdocument as inputs and writes the data and key to the appropriate datastore. The write atom 610 may provide a confirmation message thatincludes an indication whether the write operation was successful and/orthe number of records (or other types of data collection) written tostorage. The data to be stored may include, for example, a results setfrom the performance of a data query.

The read atom 620 may be used to retrieve data that has been storedusing a write atom 610. One or more key values are provided to the readatom 620. The read atom 620 accesses the XML document that correspondsto each key value provided and outputs an XML document that includes theXML documents accessed. The data accessed may, for example, be a resultsset from the performance of a data query. For example, the mapbox maymaintain a list of key values with each key value being associated witha particular XML document in a mapping data store, such as map scenariorepository 970 of FIG. 9 or map store 1030 of FIG. 10.

FIG. 7 depicts helper atoms 700 including an include atom 710, avalidate atom 720, a call atom 730, an input atom 740, and an outputatom 750. The include atom 710 provides the capability of including amap scenario within another map scenario. This may permit a particularmap scenario to be reused in a different map scenario. The ability toinclude (or nest) map scenarios may reduce the amount of time needed todevelop or maintain a map scenario. For example, some of thefunctionality needed for a map scenario may be available in anotherpreviously developed map scenario. The previously developed map scenariomay be “included” in the map scenario. Such reuse of existing code(here, a map scenario) may help reduce the time and cost required todevelop application integration software. The include atom 710 receivesa map scenario as input and invokes the received map scenario. Aninclude atom 710 may be able to be performed conditionally. This maypermit, for example, an include atom 710 that is used to provide defaultsettings to the mapbox when a particular environment settings have notbeen identified (for example, through an installation or setup process).When an include atom 710 receives a map scenario that includes one ormore other map scenarios, the include atom 710 may invoke more than onemap scenario.

The validate atom 720 allows the validation of an input XML documentagainst a particular XML schema definition (such as a World Wide WebConsortium (W3C) schema or an XML schema definition (XSD)) to determinewhether the document fulfills the required structure. The validate atom720 receives a validation rule, typically in the form of a schemadocument, that is applied to the input XML document. The validation rulemay be a complex validation rule that includes more than one validationrules. The mapbox may only access a validation rule that is availablewithin the mapstore. This may help ensure that the mapbox performs thefunction of an isolated mapping point. The validate atom 720 may beperformed conditionally. For example, a validate atom 720 may beperformed only when a debugging setting is activated. This may permithaving particular validation rules apply only during debuggingactivities without requiring a modified map scenario to be used duringdebugging. The validation results indicate whether the validation wassuccessful or not. In some implementations, the validation atom 720conditionally executes one of two mutually exclusive exits based onwhether or not the validation was successful.

The call atom 730 provides information needed to establish a connectionto a particular system and establishes the connection. Connectivityinformation may include connection parameters, such as the communicationmode (for example, synchronous or asynchronous communication), one ormore queues with which a connection is to be established, andauthentication information required by the system (for example, loginprocedures to be accessed, user names, passwords). Connectivityinformation may include connection parameters for a web service, aremote procedure call, or a remote function call.

A map scenario includes an input atom 740 and an output atom 750. Theinput atom 740 and the output atom 750 are pre-configured to identifythe location (or other type of identifier) of the input document and thelocation (or other type of identifier) where the output document is tobe placed for a particular map scenario. The input atom 740 mayrepresent an XML document that is used as an input to the map scenario.The output atom represents where the final result is placed.

The input atom and output atom each receive a document identifier andoutputs a document identifier. The output atom 750 may include more thanone document identifier when a map scenario produces more than onedocument. The document identifier may include, for example, the locationin which the document is stored or is to be stored.

FIG. 8 depicts an multi-layer architecture 800 for applicationintegration software. The multi-layer architecture 800 is divided intosix layers. From top to bottom, the layers include a business processlayer 810, an integration design pattern layer 820, a functional atomlayer 830, a data transformation rule layer 840, a data layer 850, and aphysical connection layer 860. Each particular layer leverages the oneor more layers that are below the particular layer.

The business process layer 810 may identify the application system orcomputing system with which a data exchange or other applicationintegration function is to be performed. The business process layer 810also may identify a particular service on a computing system. Forexample, business process layer 810 may refer to a particular webservice available on a host system accessible through an Internetconnection.

The integration design pattern layer 820 identifies a declarative designpattern that identifies an integration function that may be leveragedduring a data exchange or other application integration function. Anintegration design pattern may be, for example, an integration designpattern described with respect to FIGS. 3-4.

The functional atom layer 830 identifies a functional atom thatdeclaratively describes a discrete action that relates to an applicationintegration function. An example of an application integration item thatoccurs at the functional atom layer 830 is a functional atom. Functionalatoms also have been described generally in FIGS. 2-3. atoms that arerepresented as XML documents are described in FIGS. 12-16.

The data transformation rule layer 840 identifies a data transformationrule or other data transformation logic that describes how data may bechanged or transformed. For example, one or more data keys, data values,data format, or data structure may modified by a data transformationrule. An example of an application integration item in the datatransformation rule layer 840 is an XSLT stylesheet. An XSLT stylesheetdescribes how to modify data in an XML document.

The data layer 850 includes data, such as object instances, attributes,attribute values, and control data, that may be included in anapplication integration function, such as data exchange. An example ofan application integration item in the data layer 850 is a message thatincludes data to be sent from one system to another system.

The physical connection layer 860 includes the physical connection andnetwork that is used to connect two computer systems involved in anapplication integration function. An example of an applicationintegration item in the physical connection layer 860 includes a wiredor wireless WAN connection that connects two computer systems. Thephysical connection layer 870 also may include the identification of aqueuing service and access number (such as an dial-up access telephonenumber of an Internet Protocol address) that may be used to connect to aparticular computer system and service.

FIG. 9 shows the components of a software architecture 900 forintegrating application systems using a multi-layer, declarativeapproach to constructing and maintaining application integrationsoftware. The software architecture 900 has an application integrationdesigner processing component 910 and data components 920 used by theapplication integration designer. Application integration designerprocessing component 910 includes a business process flow modeller 930,design pattern visual modeller 940, a map scenario generator 950, and afunctional atom editor 960. Data components 920 include a businessprocess flow repository 965, a map scenario repository 970, and afunctional atom repository 980.

The business process flow modeller 930 produces a visual representationof a business process flow associated with an integration landscape,such as the business process flow presented in step 410 of FIG. 4 or theintegration landscape presented in step 415 of FIG. 4. The businessprocess modeller also may produce a business process flow model that isused by a developer or other user to create a map scenario, such asdescribed in steps 310-330 in FIG. 3. The business process flow modeller930 uses data about systems and what services are associated with eachsystem from the business process flow repository 965. A business processflow model may the same as or similar to the business process flowdescribed in FIGS. 3, 4 or 12.

The design pattern visual modeller 940 produces a visual representationof a declarative integration workflow associated with a particularservice connection in a business process flow. For example, the designpattern visual modeller 940 may produce a visual model that is used whena map scenario is modified, such as presenting the map scenario for aparticular service connection in step 425 of FIG. 4 and presenting alist of map scenarios from which a developer or other user may select.The design pattern modeller 940 may access, create, and/or modify dataabout design patterns from the map scenario repository 970 and/or thefunctional atom repository 980.

The functional atom editor 960 permits a developer or other user tomodify a functional atom, such as in step 470 in FIG. 4. The functionalatom editor 945 may access functional atoms stored in the functionalatom repository 980 or may access functional atoms in a map scenariostored in the map scenario repository 970. The functional atomrepository 980 may store a functional atom object, model or template forone of several types of functional atoms, such as the functional atomsshown in FIGS. 5-7. A functional atom object, for example, may be usedto create an instance of a functional atom that is used in a particularmap scenario. The modified functional atom instances are stored with orin the map scenario in the map scenario repository 970.

The map scenario generator 950 may generate a functional atom instancefrom a functional atom associated with an integration design pattern.For example, the map scenario generator 950 identifies one or morefunctional atom objects associated with an integration design pattern,for example, in a manner similar to or the same step 450 in FIG. 4. Themap scenario generator 950 instantiates a functional atom instance basedon the identified functional atom object. The map scenario generator 950also associates the functional atom instance with a particularintegration design pattern in a particular map scenario. The functionalatom instance is stored with the map scenario in the map scenariorepository 970.

FIG. 10 depicts the components of a software architecture 1000 forprocessing application integration software that includes a functionalatom. FIG. 10 uses a particular web-based implementation forillustrative purposes. The web-based implementation in FIG. 10 may bereferred to as a mapbox. The mapbox processes a map scenario thatincludes functional atoms.

The mapbox architecture 1000 may be implemented, for example, oncomputer system 110 of FIG. 1. The mapbox architecture 1000 includes aserver 1010. The server 1010 includes a processing component 1020 anddata storage 1030. The processing component 1020 includes a datatransformation processor 1035, an XML processor 1040, and an XSLprocessor 1045. Processing component 1020 may be implemented on a webserver, such as a server operating a version of Internet InformationServer by Microsoft Corporation of Redmond, Washington or an Apacheserver that operates web server software available in the public domain.Data storage 1030 may be referred to as a map store. Data componentsstored in the map store 1030 may be stored using a relational databasemanagement system that is capable of being accessed through a webserver. Examples of such a relational data management system includeSQLServer by Microsoft Corporation of Redmond, Washington and OracleDatabase by Oracle Corporation of California.

An XML document 1050 is received, for example from computer systems 115,120 or 125 of FIG. 1. The data transformation processor 1035 on themapbox server 1010 receives the XML document 1050. The datatransformation processor 1035 uses a map scenario stored in the mapstore1030 to transform the data in the received XML document. A map scenarioincludes one or more functional atoms, each of which declarativelydescribes a step in the transformation process. Functional atomsdetermine the processing flow of the map scenario and the types oftransformations to be performed in the map scenario, as described inFIGS. 5-7 and 12-16.

The data transformation processor 1035 transforms the received XMLdocument 1045 according to the functional atoms in a map scenario. Thetransformation rules may be stored in the mapstore 1030. Thearchitecture for a mapbox may permit the data transformation processorto function as an isolated mapping point. For example, softwarearchitecture 1010 provides the map store 1030, the XML document to betransformed, and a private data store that includes the requiredtransformation and validation rules. All the data required by the mapscenario to transform the XML document is present within the softwarearchitecture and input document. The data transformation processor 1035does not access data stored in other data management systems (forexample, application specific code stored in an application system) toaccomplish the data transformation.

Typically, the data transformation processor 1035 may create one or moreintermediate XML documents as directed by the particular functionalatoms in the map scenario. The data transformation processor 1035applies various transformation atoms in the map scenario. An XMLdocument may be processed by the XML processor 1040 and the XSLprocessor 1045. For example, an XSLT stylesheet is applied by the XSLprocessor 1045 to the XML document during the transformation. Thetransformed XML document 1060 is output.

In some implementations, the transformed XML document 1060 may befurther transformed into a format other than an XML document. In someimplementations, the data transformation processor 1035 may receive datathat is stored in a format other than XML. In such a case, the datatransformation processor 1035 preprocesses the received document into anXML format and proceeds as described above.

An operating environment for a software architecture 1000 may includeversion of Java (a programming language developed by Sun Microsystems,Inc. of Santa Clara, Calif.); a relational database management systemsuch as SQL-Server or Oracle that is accessible to Java programs througha Java database connectivity program; and an XML processor that supportsa document object model, XSLT with scripting, and includes a validatingparser capable of validating an input document using a document typedefinition. A Java class instance may be created for each type offunctional atom, and the necessary functional atoms may be instantiatedat runtime for a particular map scenario. Other implementations may useother operating environments, for example, an operating environment thatincludes software developed using the C++ programming language or theVisual Basic programming language.

FIG. 11 shows a process 1100 for transforming data using functionalatoms to transform data from a Customer Relationship Management (“CRM”)order entry system to a format that is accepted by an order processingsystem. The process 1100 may be performed by the data transformationprocessor 1035 (which may be referred to as a mapbox processor) of FIG.10. The process 1100 begins when a mapbox processor receives an XMLdocument 1110 containing customer data, order data, and product data,such as order data 210, 215, 220 or 225 of FIG. 2. The mapbox processoruses map scenario data 1115 that includes the data required to performthe transformations defined in the map scenario to be performed by themapbox processor. The map scenario includes a customer/order branch atom1130, an order/product branch atom 1132, a product split atom 1135, atransform customer atom 1137, a transform order atom 1140, transformproduct atoms 1142, 1145 and 1147, a join products atom 1150, anunbranch order/product atom 1152, and an unbranch customer/order atom1155. Collectively, these atoms transform the received XML document 1110into the transformed XML document 1160 that is the result of the mapscenario 1120.

The mapbox processor invokes the customer/order branch atom 1130 usingthe received XML document 1110. The customer/order branch atom 1130produces a customer XML document 1162 that includes the customer datafrom XML document 1110. The customer/order branch atom 1130 alsoproduces XML document 1164 that includes the order data and product datafrom XML document 1110.

The mapbox processor invokes the transform customer atom 1137 usingcustomer XML document 1162 to transform one or more fields within thecustomer XML document 1162. For example, the mapbox processor may enrichthe customer data by adding default data. The mapbox may transform datavalues, such as replacing a particular translation value with adifferent value that corresponds to the replaced value as describedpreviously with respect to FIG. 2. The transformed customer data isoutput as XML document 1166. The mapbox processor sends customer XMLdocument 1166 to the unbranch customer/order atom 1155. The unbranchcustomer/order atom 1155 waits to receive the order input XML documentbefore processing the received customer XML document 1166.

The mapbox processor invokes the order/product branch atom 1132 with theXML document 1164 as input. The order/product branch atom 1132 producesan order XML document 1168 that includes order data in the received XMLdocument 1164. The order/product branch atom 1132 also produces aproduct XML document 1170 that includes the product data in the receivedXML document 1164.

The mapbox processor invokes the transform order atom 1140 with theorder XML document 1168 as input. The mapbox processor transforms theorder XML document 1168 as directed by the XLST stylesheet associatedwith the transform order atom 1140. For example, the mapbox processormay transform key values, such described previously with respect to FIG.2. The mapbox processor may transform data value formats, such as thedate format transformation described previously with respect to FIG. 2.The transform order atom 1140 outputs a transformed order XML document1172 that is used as an input to order/product unbranch atom 1152. Theorder/product unbranch atom 1152 waits for additional input beforeprocessing the received transformed order XML document 1172.

The product split atom 1135 is invoked with the product XML document1170 produced by the order/product branch atom 1132. The product splitatom 1135 divides the repeating product data for products 1, 2 and 3into product XML documents 1175, 1178, and 1180. A transform productatom 1142, 1145 or 1147 is invoked with one of the three product XMLdocuments 1175, 1178 or 1180. The transform product atoms 1142, 1145 and1147 transform the received product XML document 1175, 1178 or 1180 to atransformed product XML document 1182, 1185 or 1187 based on an XLSTstylesheet associated with the transform product atom. The transformproduct atoms 1142, 1145 and 1147 are instantiations of the sametransform product atom. The transform product atoms 1142, 1145 and 1147may be invoked in parallel which may provide for efficiency improvementsin processing the map scenario. Each of the transformed product XMLdocuments 1182, 1185 and 1187 is provided to the join products atom1150.

When the join products atom 1150 has received all of the transformedproduct XML documents 1182, 1185 and 1187, the join products atom 1150assembles the separate transformed product XML documents 1182, 1185 and1187 into a single transformed product XML document 1190. Thetransformed product XML document 1190 is provided to the order/productunbranch atom 1152. When the order/product unbranch atom 1152 hasreceived both the transformed product XML document 1190 and thetransformed order XML document 1172, the order/product unbranch atom1152 assembles the separate XML documents 1172 and 1190 into a singletransformed order/product XML document 1192. The transformedorder/product XML document 1192 is provided to the customer/orderunbranch atom 1155. When the customer/order unbranch atom 1155 hasreceived both the transformed order/product XML document 1192 and thetransformed customer XML document 1166, the customer/order unbranch atom1155 assembles the separate XML documents 1192 and 1166 to thetransformed customer/order/product XML document 1160 that is the outputfrom the mapbox processor after executing the map scenario.

FIG. 12 is an example of an XML representation of a map scenario 1200.In general, the map scenario 1200 includes the assembled functionalatoms that may be executed when the map scenario 1200 is invoked. Asillustrated in FIGS. 12-16, each of the functional atoms includes adescription, an input identifier, and an output identifier. Thedescription is a textual description that may be associated with aninstance of the functional atom. The textual description tag may provideinternal documentation and allow a developer or other user todistinguish a functional atom without requiring the developer to readthe text or other code within a functional atom. The textual descriptionmay be viewable in the application integration workstation.

The input identifier and output identifier are the means by whichfunctional atoms are connected to form a data and process flow. Theinput identifier and output identifier collectively form a unique pathof connectivity between any two functional atoms. The path is identifiedby an output identifier of a predecessor atom and the input identifierof the successor atom. Error checking is performed by the mapbox toensure that the path is unique, each input identifier matches an outputidentifier of another functional atom, and each output identifiermatches an input identifier of another functional atom. Most types offunctional atoms include one input identifier and one output identifier.Some types of functional atoms permit more than one input identifierand/or more than one output identifier.

The input identifier of a particular functional atom points to thepredecessor atom (for example, the functional atom precedes theparticular functional atom in a processing flow of the map scenario). Aninput identifier with a value of zero identifies the entry point intothe map scenario where an application system feeds data (here, an XMLdocument) into the map scenario.

The output identifier of a particular functional atom points to thesuccessor atom (for example, the functional atom that follows theparticular functional atom in the processing flow of the map scenario).An output identifier with a value of zero identifies the exit point ofthe map scenario where the overall output (for example, the transformedXML document output, as in item 1060 in FIG. 10) of the map scenario.

The map scenario includes a map scenario header 1210, functional atoms1215, and optional data converter information 1220. The map scenarioheader 1210 includes execution path information 1230, a name 1235, adescription 1237, a status indicator 1238, and a header wrapper 1210Wthat denotes a closing delimiter for the map scenario. Execution pathinformation 1230 includes the location of some of the physical filesassociated with the map scenario. In this implementation, the mapstoreuses a uniform resource locator (URL) reference. The URL format used isonly valid for storage controlled by the mapbox. This may providesecurity because the retrieval the transformation documents stored inthe mapstore may only be performed by the mapbox. Some implementationsmay include an authorization process that permits only authorized usersor processes to accessing the mapstore. In some implementations, othertypes of URL references, including public URL references, may be used.

The name 1235 identifies a name for the map scenario. The description1237 includes a description of the map scenario. The name 1235 anddescription 1237 provide internal documentation and may help a developeror other user to identify a particular map scenario and understand thefunction of the map scenario. The name 1235 and description 1237 may bepresented in a user interface to help a developer or other user toidentify a particular a map scenario. For example, the name 1235 anddescription 1237 associated with several map scenarios may be presentedin a user interface that permits a developer or other user to identify aparticular map scenario to be modified. The status indicator 1238identifies the status of the map scenario. For example, the statusindicator 1238 may indicate whether the map scenario is active or not. Amapbox may only execute map scenarios with a status of active. This maypermit a developer to indicate whether the particular map scenario isavailable for use or testing.

The functional atoms 1215 includes the assembled functional atoms thatare included in the map scenario. The functional atoms 1215 include abranch atom 1240, an include atom 1250, a transform atom 1260, and anunbranch atom 1270.

The branch atom 1240 includes a name 1242 and a description 1244 thatmay help a developer or other user to identify a particular atom andunderstand the function of the atom. The branch atom includes an inputidentifier tag 1246 with a value of 0. This indicates that the mapscenario will process the branch atom 1240 before processing any otherfunctional atoms. The branch atom 1240 includes output identifier tags1247, 1248, and 1249. The output identifier tags 1248 identify threeprocessing paths in map scenario 1200. The mapbox may direct processingfrom the branch atom 1240 to the include atom 1250 based on a match ofthe output identifier tag 1247 in the branch atom 1240 with the inputidentifier tag 1252 of the include atom 1250.

The include atom 1250 includes a name 1254 and a description 1256 tohelp a developer identify the particular atom and understand thefunction performed by the functional atom. The include atom 1250 callsanother map scenario that is identified by include information 1257.Here, include information 1257 includes a name of the map scenario to beinvoked and a name of a dataset that is used by the map scenario. Thecapability to include one or more map scenarios within a map scenariomay permit a developer to reuse map scenarios that have been developed.The capability to reuse a map scenario may help reduce the time and costof developing and maintaining application integration software. Thecapability to include one or more map scenarios within a map scenarioalso may help a developer understand the processing performed by a mapscenario by reducing the complexity of any one map scenario. This mayhelp reduce the time and cost of developing and maintaining applicationintegration software.

After the processing of the included map scenario is completed, themapbox directs processing to the functional atom identified by theoutput identifier tag 1258. The output identifier tag 1258 of theinclude atom 1254 matches the input identifier tag 1272 of the unbranchatom 1270. The unbranch atom 1270 includes a name 1274 and a description1276 to help a developer identify the particular atom and understand thefunction performed by the functional atom. After completing any unbranchprocessing associated with unbranch atom 1270, the mapbox completesprocessing the map scenario 1200 as indicated by the output identifiertag 1277 of the unbranch atom 1270. Unbranch atom 1270 has an outputidentifier value of 0 that indicates that the map scenario has completedprocessing all functional atoms associated with the map scenario.

Alternatively to processing the document received by the mapbox usingthe included map scenario (by directing processing to the include atom1250), the mapbox may direct processing from the branch atom 1240 to thetransform atom 1260 based on a match of the output identifier tag 1248in the branch atom 1240 with the input identifier tag 1282 of thetransform atom 1260. The transform atom 1260 includes a name 1284 and adescription 1286 to help a developer identify the particular atom andunderstand the function performed by the functional atom. The mapboxtransforms the data in the received document by applying the datatransformation rules included in XSLT stylesheet identified in rule1288. Alternatively, transform atom 1260 may have included the datatransformation rules themselves in rule 1288. The mapbox proceeds todirect processing to the unbranch atom 1274 that has input identifiertag 1278 that matches the output identifier tag 1289 in the transformatom 1260.

Alternatively to processing the document received by the mapbox using anincluded map scenario (by directing processing to the include atom 1250)or transforming the document received (by directing processing to thetransform atom 1260), the mapbox may direct processing from the branchatom 1240 directly to the unbranch atom 1270. The mapbox so directsprocessing based on a match of the output identifier tag 1249 in thebranch atom 1240 with the input identifier tag 1279 of the unbranch atom1270. In this manner, the document received may be routed to the outputof the mapbox without undergoing any data transformation. Such routingmay be useful, for instance, when a invalid document has been received.

The data converter information 1220 includes conversion rules to convertdata for a map scenario to an XML document when the data is otherwiseformatted (e.g., data formatted as a comma-delimited file). Theconversion rules may be included in an executable program developed, forexample, in Java Visual Basic (VB), Javascript, or VBscript.

FIG. 13 shows an example representation in XML of a transform atom 1300.The transform atom 1300 includes a header 1310 that includes a name1312, a description 1314, and a header wrapper 1310W that denotes aclosing delimiter for the transform atom 1300. As described in FIG. 12,the name 1312 and description 1314 may provide internal documentationand help to distinguish a particular functional atom from otherfunctional atoms. The transform atom 1300 also includes an inputidentifier 1320 and an output identifier tag 1325 that are the means bywhich functional atoms are interlinked to form a data and process flow,as described in FIG. 12.

The transform atom 1300 includes rule information 1330. The ruleinformation 1330 may include the data transformation rules themselves.This may be referred to as in-line transformation. Additionally oralternatively, the rule information 1330 may point to another documentthat includes the data transformation rules to be applied. Here, ruleinformation 1330 points to an XSLT stylesheet that includes datatransformation rules to be applied. The use of a separatedtransformation document may be useful. For example, the transformationrules may be used in a different map scenario or elsewhere in the samemap scenario. The separation of the data transformation rules from thetransform atom in the map scenario reduces the size and cognitivecomplexity of the transform atom and the map scenario. This may helpreduce the time and cost of the construction and maintenance of theapplication integration software by increasing the comprehensibility ofthe map scenario.

FIG. 14 depicts an example representation in XML of a split atom 1400.The split atom 1400 includes a header 1410 that includes a name 1412, adescription 1414, and a header wrapper 1410W that denotes a closingdelimiter for the split atom. As described in FIG. 12, the name 1412 anddescription 1414 may provide internal documentation and help todistinguish a particular functional atom from other functional atoms.The split atom 1400 also includes an input identifier 1420 and an outputidentifier tag 1425 that are the means by which functional atoms areinterlinked to form a data and process flow, as described in FIG. 12.

The output identifier of the split atom 1400 includes an “xpath”expression that is applied to the input document. The expression splitsthe input document into zero or more separate documents. The expressionis an array of elements that identifies the root of each documentproduced by the split atom.

FIG. 15 depicts an example representation in XML of a branch atom 1500.The branch atom 1500 includes a header 1510 that includes a name 1512, adescription 1514, and a header delimiter 1510 W that denotes a closingdelimiter for the branch atom. As described in FIG. 12, the name 1512and description 1514 may provide internal documentation and help todistinguish a particular functional atom from other functional atoms.The branch atom 1500 also includes an input identifier 1520 and outputidentifier tags 1525, 1526, and 1527 that are the means by whichfunctional atoms are interlinked to form a data and process flow, asdescribed in FIG. 12.

The output identifiers 1525 and 1526 of the branch atom 1500 eachinclude an expression (here, an “xpath” expression) that detects whethera particular process should be performed for all or a portion of thedocument received by the branch atom 1500.

The output identifier 1527 is used to specify the processing that willbe performed (for example, the functional atom that will next be invokedby the mapbox) when neither the condition identified by the expressionidentified by output identifier 1525 or the condition identified by theexpression identified by output identifier 1526 is not fulfilled. Thismay be referred to as an “otherwise exit” or default processing.

FIG. 16 depicts an example representation in XML of a validate atom1600. The validate atom 1600 includes a header 1610 that includes a name1612, a description 1614, and a header wrapper 1610W that denotes aclosing delimiter for the validate atom. As described in FIG. 12, thename 1612 and description 1614 may provide internal documentation andhelp to distinguish a particular functional atom from other functionalatoms. The validate atom 1600 also includes an input identifier 1620,output identifiers 1625 and 1630 that are the means by which functionalatoms are interlinked to form a data and process flow, as described inFIG. 12.

The validate atom 1600 includes schema information 1640. Schemainformation 1640 identifies an XML schema definition document (forexample, a W3C schema or a XSD schema) that is to be applied to thedocument received by the validate atom to determine whether the documentfulfills the rules included in the XML schema definition. Additionallyor alternatively, schema information may include the schema informationdirectly in the validate atom 1600 in contrast to a reference to aschema definition document.

The output identifiers 1625 and 1630 identify two mutually exclusiveprocessing paths that are executed based on whether or not thevalidation against the schema information was successful. When thedocument does not fulfill the rules (for example, a validation erroroccurs), the output identifier 1630 is executed. Typically, the data anda tag in the output document contains the results of the validation thathas happened.

The validation results may be used by the developer or other user for tomonitor the map scenario processing. The validation results also may beused by the developer or other user for problem solving. For example,during development of a map scenario, validation atom 1600 may be usedto order to check the correctness of a received document before furtherprocessing. The validation atom 1600 also may be used immediately beforethe final output of the map scenario from the mapbox to check thecorrectness of the output document.

FIGS. 17-18 depict an example of a user interface for visually modelingapplication integration software. FIG. 17 presents a business processflow 1700 including a CRM system 1710, a supplier system 1715, a orderprocessing system 1720, a financial management system 1725, and abusiness data warehouse system 1730. The systems presented in thebusiness process flow 1700 may be controlled by the same or differentcorporate entities. For example, one corporate entity may control theCRM system 1710, the order processing system 1720, a financialmanagement system 1725, and a business data warehouse system 1730. Adifferent corporate entity may control the supplier system 1715. Eachsystem is represented in the business process flow 1700 as a rectanglewith text identifying the system. The one or more services that areavailable from that system are listed in the user interface. Here, eachservice is represented as a box that appears within the borders of thesystem rectangle. The CRM system 1710 includes a create quotationservice 1735 and a create sales order service 1737. The supplier systemincludes a check product availability service 1740 and a process salesorder service 1742. The order processing system 1720 includes areplicate sales order service 1745 and a place sales order service 1747.The financial management system 1725 includes a perform credit checkservice 1750 and a perform order profit analysis service 1752. Thebusiness data warehouse 1730 includes an update quotation trackingservice 1760 and a update sales tracking service 1762.

The developer or other user may insert or delete systems from thepresented business process flow 1700. Similarly, the developer or otheruser may insert or delete services from systems in the presentedbusiness process flow 1700. The developer or other user connects aparticular service with one or more services in the integrationlandscape. In the business process flow 1700 a line drawn between twoservice boxes indicate a service connection. The business process flow1700 includes service connections 1770, 1772, 1774, 1776, 1778, 1780,1782, and 1784. The developer or other user may indicate an integrationdesign pattern flow for one or more service connections in the businessprocess flow 1700, as described in FIG. 18.

Referring also to FIG. 18, a developer or other user may indicate anintegration design pattern flow for service connections 1776 and 1782.Service connection 1776 represents the data exchange between the createsales order service 1737 in the CRM system 1710 with the replicate salesorder service 1745 in the order processing system 1720. Serviceconnection 1782 represents the data exchange between the replicate salesorder service 1745 and the place sales order service 1747, both of whichare in the order processing system 1720.

FIG. 18 depicts an example of a user interface 1800 that may be used bya developer or other user to create and modify an integration designpattern flow. A user may design a conceptual data and process flow usingintegration design pattern building-blocks that indicate the datatransformation needed to accomplish the data exchange required in one ormore service connections.

The user interface 1800 includes windows 1810 and 1820. The userinterface 1800 includes a window 1810 that includes set of integrationdesign patterns 1830-1836. Each integration design pattern isrepresented as a box within window 1810. For brevity, only a fewillustrative integration design patterns are included in window 1810.Window 1810 also may be referred to as a palette of integration designpatterns. A user may select a particular integration design pattern fromwindow 1810 for use in the integration design pattern flow presented inwindow 1820. For example, the user may double-click on a particularintegration design pattern from the set of integration design patterns1830-1836. The user may drag-and-drop the selected integration designpattern into window 1820. The user may indicate the position in whichthe selected integration design pattern should be inserted into theintegration design pattern flow in window 1820. The user may connect oneor more integration design patterns together in window 1820.

Here, a particular integration design pattern flow produced by a user isdepicted. The integration design pattern flow in window 1820 includesthe integration design patterns 1850, 1855, 1860, 1865, 1870, and 1875.The integration design patterns are connected into a flow using lines.The flow begins with integration design pattern 1850 that indicates theinput document should be validated to ensure that all mandatoryinformation is present. The flow indicates that the document then issplit into multiple documents (as indicated by integration designpattern 1855). The integration design pattern flow indicates thatcustomer information on each of the documents should be transformed (asindicated by integration design patterns 1860 and 1865). Eachtransformed document may be provided to different sales vendors. Theintegration design pattern flow indicates that the flow is competed withcalls to the place sales order service (as indicated by integrationdesign patterns 1870 and 1875).

FIG. 19 depicts the functional atoms that may be generated by theapplication integration workstation for the integration design patternflow presented in window 1820 in FIG. 18. The generation of functionalatoms from a integration design pattern has been described in FIGS. 3and 4. Functional atoms and functional atom templates have beendescribed previously in FIGS. 5-7 and 12-16.

A validate atom 1950 is generated based on integration design pattern1850. A split atom 1955 is generated based on integration design pattern1855. An include atom 1960 is generated based on integration designpattern 1860. The include atom 1960 may include more than one functionalatoms, such as a validate atom to validate customer information, atransform atom to perform key mapping for customer information, and atransform atom to perform additional data value transformations, such assimple table lookup or one-to-one data value transformations. Similarly,an include atom 1965 is generated based on integration design pattern1865 to transform customer information and, like include atom 1960, mayinclude more than one functional atoms to perform the functions relatedto integration design pattern 1865. The call atom 1970 is generatedbased on integration design pattern 1870, and the call atom 1975 isgenerated based on integration design pattern 1875.

FIGS. 20-21 illustrate particular implementations of a mapbox, such asthe mapbox described in FIGS. 9-10. In FIGS. 20-21 a CRM systemexchanges data with a groupware system, through a groupware server, toprovide the groupware system with contact, appointment, and/or taskinformation (groupware data) from the CRM system. Examples of agroupware server include a Microsoft Exchange Server by MicrosoftCorporation of Redmond, Washington and a Lotus Domino Groupware Serverby IBM Corporation of White Plains, N.Y.

FIG. 20 depicts a CRM server 2010 providing data to a groupware server2020. The CRM server 2010 includes CRM middleware 2030. The CRMmiddleware 2030 directs data exchange messages between the CRM serverand other systems (not shown), including the groupware server 2020. Ingeneral, the CRM middleware 2030 uses different types of messagestructures to communicate different data structures. The CRM middleware2030 sends a message that includes groupware data from the CRM server2010 to groupware adapter 2040. The groupware adapter 2040 receives themessage from the CRM middleware 2030. The groupware adapter 2040transforms the groupware data into an intermediate groupware format andsends the message to the groupware connector 2050. For example, thegroupware adapter 2040 may receive CRM data for a customer or otherbusiness partner. The groupware adapter 2040 may transform the customerdata into an intermediate groupware contact format (such as vCard, aformat for transporting groupware contact information). Similarly, thegroupware adapter 2040 may receive CRM data for an activity or otherresource management data. The groupware adapter 2040 may transform theactivity data into an intermediate groupware calendar format (such asiCal, a format for transporting groupware calendar information).

The groupware connector 2050 receives the message from the groupwareadapter 2040 and transforms the data from the intermediate groupwareformat to a format that is understandable by groupware server 2020. Forexample, if the groupware server is a Microsoft Exchange server, thegroupware connector 2050 transforms the groupware data into a formatreadable by a Microsoft Exchange groupware server. Similarly, if thegroupware server is a Lotus Domino server, the groupware connector 2050transforms the groupware data into a format readable by a Lotus Dominogroupware server. The groupware connector 2050 then sends thetransformed groupware data to groupware server 2020. The groupwareserver 2020 receives the transformed groupware data and updates the datastored on the groupware server 2020. For example, the groupware server2020 may insert, for example, groupware information relating to a newcontact into a groupware address book or contact list. The groupwareserver 2020 may insert a new task and/or a new appointment based on thetransformed data received. The groupware server 2020 sends anacknowledgement message to the CRM middleware 2030 through the groupwareconnector 2050 and the groupware adapter 2040.

In some implementations, a groupware adapter 2040 may transform thereceived CRM data into a format understandable to the groupware server2020. In such a case, the groupware connector 2050 may not be necessary.

In some cases, the groupware connector may update the groupwareinformation stored on the groupware server 2020. For example, thegroupware connector may use a remote procedure call or other type ofprotocol that allows a program on one computer system to execute aprogram on a server computer system.

Referring to FIG. 21, the groupware connector 2110 functions as a bridgebetween a CRM groupware adapter 2115 (such as groupware adapter 2040 inFIG. 20) in a CRM server, such as CRM server 2010 in FIG. 20. Thegroupware connector 2110 communicates with the groupware adapter 2115through the use of a transfer protocol 2125 (such as the Simple ObjectAccess Protocol (SOAP) protocol over the HTTP protocol). Messages thatinclude data from the CRM server are sent from the groupware adapter2115 to the groupware server 2120. A message that includes groupwaredata may relate to a function of the groupware running on the groupwareserver 2120. Examples of groupware functions include the maintenance ofa calendar of appointments and meetings for a user or other entity, atask or “to do” list for a user or other entity, or an address book orcontact list for a user or other entity. Typically, a message identifiesone or more users to receive a message or groupware data update. Thegroupware server 2120 includes a mailbox for each groupware user 2122and groupware data storage 2123. A mailbox for a groupware user includesinformation associated with a calendar 2126 of appointments or meetingsfor the user and one or more tasks in a “to do” list2128. Groupware datastorage 2124 includes documents or other data stored in the groupwareserver 2120. The groupware data storage 2123 may include a databaseand/or another data management system. For example, groupware datastorage 2123 may include a collection of publicly-accessible documentfolders that hold groupware data.

The messages to be sent from the groupware adapter 2115 are put into oneof several queues 2130-2133. Messages with CRM data to be sent to thegroupware server 2120 are placed in a message queue 2130 by thesyncpoint 2135. (The other queues 2131-2133 are described later.) Thesyncpoint 2135 may implement aspects of CRM Middleware 2030 in FIG. 20.The syncpoint 2135 may create the queues 2130-2133 used by CRM groupwareadapter 2115. In some implementations, the syncpoint 2135 may include orperform the functions of a CRM groupware adapter 2040 of FIG. 20 or CRMgroupware adapter 2115.

The groupware connector 2110 invokes the groupware adapter 2115 toaccess one or more messages in the queues 2130-2133. In someimplementations, the groupware connector 2110 may include a messagequeue, and the syncpoint 2135 or the groupware adapter 2115 may place amessage in the message queue of the groupware connector.

Each message provided by the groupware adapter 2115 includes of a headerand a message body. The header may contain information specific to theCRM system. The header, for example, may include a unique CRM documentidentifier that may be used for subsequent item updates to the data sentin the message. The header may include a groupware item identifier thatcorresponds to a unique identifier for the data used by the groupwareserver 2120. For data to be added to the groupware data storage 2123 orone or more mailboxes 2122 on the groupware server 2120, the groupwareitem identifier is empty when the message including the groupware datafrom the CRM server is sent to the groupware server 2120. The groupwareitem identifier may be created when the data is inserted into thegroupware server 2120 and returned to the CRM server through thegroupware connector 2110, groupware adapter 2115, and syncpoint 2135 inan acknowledgement message. The groupware item identifier may helpidentify the data in the groupware server database during subsequentupdates. In addition, some header information, such as the unique CRMdocument identifier and/or the groupware item identifier may be storedin a log file for the message. The log file may be used to help identifyand solve problems with processing particular messages or user queues.

The header information includes an address of the recipient, such as ane-mail address. This may enable the groupware server to storeinformation (such as appointments and tasks) in a particular user'smailbox. Some groupware servers may stored contacts in a separatedatabase or other data storage (such as a publicly-accessible folder)that is accessible through an external simple mail transfer protocol(SMTP) e-mail address or other type of e-mail address. The e-mailaddress may be included in the address of the recipient in the header.

The body includes a record containing transformed groupware data fromthe CRM server. The groupware adapter 2115 converts the CRM server datainto a groupware format, such as a common groupware format (vCard for acontact and iCal for tasks and appointments). The groupware connector2110 transforms the received data from the common format (for example,iCal or vCard) to a format specific to Lotus Domino. The datatransformations may be performed using, for example, XSLTtransformations. For example, Lotus Domino uses data in the commonformat vCard for a contact. Similarly, the body in a message may includetask or appointment data in a format readable by the groupware server2120, such as data in the common format iCal for tasks and appointmentsthat is readable by Lotus Domino.

The groupware connector 2110 uses a transfer protocol 2140 to connect tothe groupware server 2120. When a message includes a new contact, thegroupware connector 2110 opens the groupware data storage, saves thedata in the data storage, and sends any document identifier associatedwith the saved data to the groupware adapter through an identifier queue2132 that is described below.

When a message includes an appointment that has more than oneparticipant, the groupware connector 2110 stores a message in thecalendar of the person identified as organizing the appointment and ameeting request is sent to the mailbox of all other participants.

When a message includes data to be updated in the groupware server 2120,the connector opens a document, updates the fields and saves thedocument back to the groupware data storage 2123. When the messageincludes data to be updated in the groupware server 2120 and the data tobe updated is not found in the groupware data storage 2123, thegroupware connector 2110 may create and save a new document with thedata. When a message requires the deletion of an original item in thegroupware server 2120, the groupware connector 2110 opens a document anddeletes it.

When a message is successfully processed, the groupware connector 2110sends a confirmation or acknowledgement message to the groupware adapter2115. The groupware adapter 2115 then may delete the message from thequeue.

The groupware connector 2110 includes error logs 2150-2152 that areprocessed by a logging process (or logger) 2155. The groupware connector2210 includes a connection 2160 for processing messages of users. Insome implementations, a connection pool that includes a set of threadsor connections may be used. The messages for different users may beprocessed in parallel using different threads in the connection pool.The message queue for a single user is always processed in a singlethread. The amount of threads used to transfer data may be userdefinable.

The groupware connector 2110 uses a set of queues 2131-2133 tocommunicate with the groupware adapter 2115. The notify queue 2131 is aninbound queue that includes information about data availability in otherqueues. The identifier queue 2132 is an outbound queue that includesinformation about the groupware unique identifiers for newly writtendocuments. The groupware connector 2110 posts information to theidentifier queue 2132. The protocol queue 2133 includes informationabout errors that have occurred.

Advantages may be found when the computing environment of the groupwareconnector 2110 is compatible with the computing environment of thegroupware server 2120 with which the groupware connector is tocommunicate. For example, when communicating with a Lotus Dominogroupware server, a groupware connector developed using the Javaprogramming language may be beneficial. The groupware connector 2110 mayuse a transfer protocol 2140 that uses a Lotus Java/COBRA applicationprogramming interface (API) to send data to and receive data from theLotus Domino groupware server. Similarly, when communicating with aMicrosoft Exchange Server, a groupware connector developed using the C++programming language may be useful. The groupware connector 2110 may usea transfer protocol 2140 that uses a common document object (CDO)protocol may be used to send data to and receive data from the MicrosoftExchange Server.

Although FIGS. 20-21 illustrate a one-way data exchange from a CRMsystem to a groupware system, the illustrated techniques may beapplicable to a two-directional data exchange (for example, thegroupware system also may provide data to the CRM system). Thetechniques also may be applicable to the exchange of data types otherthan the illustrated contact, appointment, and task information.

Implementations may include a method or process, an apparatus or system,or computer software on a computer medium. It will be understood thatvarious modifications may be made. For example, advantageous resultsstill could be achieved if steps of the disclosed techniques wereperformed in a different order and/or if components in the disclosedsystems were combined in a different manner and/or replaced orsupplemented by other components.

The benefits from the described application integration techniques arenot limited to the illustrated implementations. For example, someimplementations may different data management systems, data structures,or system configurations.

Some implementations may store data for the application in anobject-oriented database that physically organizes data into a series ofobjects, a relational database, or another type of data managementsystem. A relational database may logically organize data into a seriesof database tables, each of which may arrange data associated with anentity in a series of columns and rows. Each column may describe anattribute of the entity for which data is being stored, while each rowmay represent a collection of attribute values for a particular entity.

1. A computer system for use in the design of application integrationsoftware that performs data exchange between at least two applicationsystems, the computer system comprising a processor connected to astorage device and at least one input/output device, wherein theprocessor is operable to execute: a design modulate configured todesign, based on user input, a declarative integration workflow thatincludes predefined integration design patterns that collectivelydescribe a data exchange between at least two application systems,wherein: an integration design pattern identifies integration functionsused in the data exchange between at least two application systems, anintegration function identifies a process used in data transfers, andthe at least two application systems each use a database capable ofstoring data related to business transactions and instructions, thatwhen executed, cause data related to the business transactions to beprocessed; a sequencing module configured to specify, based on userinput, a sequence for performing the integration design patterns tocause the data exchange; and a storage module configured to store thedeclarative integration workflow such that the declarative integrationworkflow is to be used to generate software codes that, when executed,performs the data exchange.
 2. The computer system of claim wherein thedesign module is further configured to represent predefined integrationpatterns from which a user may select to be included in the declarativeintegration flow.
 3. The computer system of claim 1 wherein at least onepredefined integration design pattern includes at least one of a patternfor validating a data collection for mandatory information, a patternfor splitting data from one data collection into separate datacollections, a pattern for invoking a key mapping function, a patternfor invoking a data transformation function, a pattern for invoking aconnectivity function for a particular application system, and a patternfor invoking a connectivity function for invoking a particular service.4. The computer system of claim 1 wherein the design module is furtherconfigured to represent at least one integration design pattern thatdecomposes into two or more integration design patterns and from which auser may select to be included in the declarative integration workflow.5. The computer system of claim 1 wherein the design module is furtherconfigured to represent at least two application systems between whichdata is to be exchanged in a declarative integration workflow.
 6. Thecomputer system of claim 1 wherein the design module is furtherconfigured to represent at least two application services between whichdata is to be exchanged in a declarative integration workflow.
 7. Thecomputer system of claim 6 wherein the design module is furtherconfigured to associate an application service with an applicationsystem.
 8. The computer system of claim 1 wherein the design module isfurther configured to represent the data to be exchanged between atleast two application systems.
 9. The computer system of claim 8 whereinthe design module is further configured to represent at least one typeof data.
 10. The computer system of claim 8 wherein the design module isfurther configured to represent at least one data collection to beexchanged.
 11. The computer system of claim 10 wherein the design moduleis further configured to represent at least one of an object, an objecttype, an object instance, a database table, a database segment, adatabase table row, a document capable of being accessed thorough aformat that may be transmitted by an Internet Protocol, an XML-document,a text file, a binary file, and a message.
 12. The computer system ofclaim 1 further comprises a generative module configured to generateapplication integration software based on the declarative integrationworkflow.
 13. The computer system of claim 12 herein the generativemodule is further configured to generate a template for applicationintegration software.
 14. The computer system of claim 12 herein thegenerative module is further configured to generate source code.
 15. Thecomputer system of claim 12 wherein the generative module is furtherconfigured to generate executable instructions for a computer.
 16. Thecomputer system of claim 12 wherein the generative module is furtherconfigured to permit a user to modify the generated applicationintegration software.
 17. The computer system of claim 12 wherein thegenerative module is further configured to associate the generatedapplication integration software with the declarative integrationworkflow.
 18. The computer system of claim 17 wherein the generativemodule is further configured to associate at least one portion of thegenerated application integration software with the at least one portionof the declarative integration workflow, each particular portion of thegenerated application integration software being associated with aparticular portion of the declarative integration workflow.
 19. Thecomputer system of claim 12 wherein the generative module is furtherconfigured to generate application integration software based on a layerof application integration.
 20. The computer system of claim 19 whereinthe generative module is further configured to generate applicationintegration software based on at least one of a business process layer,an integration design pattern layer, a functional atom layer, a datatransformation rule layer, a data layer, and a physical connectionlayer.
 21. The computer system of claim 20 wherein the business processlayer identifies at least one application system with which anapplication integration function is to be performed.
 22. The computersystem of claim 20 wherein the business process layer identifies atleast one service, each service being associated with an identifiedapplication system.
 23. The computer system of claim 20 wherein theintegration design pattern layer specifies at least one declarativedesign pattern that identifies an integration function used during anapplication integration function.
 24. The computer system of claim 20wherein the functional atom layer identifies at least one functionalatom that declaratively describe an action that relates to anapplication integration function.
 25. The computer system of claim 20wherein the data transformation rule layer specifies data transformationlogic that describes how data is transformed.
 26. The computer system ofclaim 25 wherein the data transformation logic comprises a datatransformation rule.
 27. The computer system of claim 20 wherein thedata layer that specifies data included in an application integrationfunction.
 28. The computer system of claim 27 wherein the data includedin an application integration function comprises at least one of anobject instance, an attribute, an attribute value and control dataincluded in an application integration function.
 29. The computer systemof claim 20 wherein the physical connection layer comprises a physicalconnection layer that identifies or includes s physical connection andnetwork that is used to connect two computer systems involved in anapplication integration function.
 30. A design workstation andaccompanying user interface for use in the design of applicationintegration software that performs data exchange between at least twoapplication systems, the software design work station comprising aprocessor connected to a storage device and at least one input/outputdevice, wherein the processor is operable to execute: a design moduleconfigured to design, based on user input, a declarative integrationworkflow that includes predefined integration design patterns thatcollectively describe a data exchange between at least two applicationsystems, wherein: an integration design pattern identifies functionsused in the data exchange between at least two application systems, anintegration function identifies a process used in data transfers, andthe at least two application systems each use a database capable ofstoring data related to business transactions and instructions, thatwhen executed, cause data related to the business transactions to beprocessed; a sequencing module configured to specify based on userinput, a sequence for performing the integration design patters to causethe data exchange; and a storage module configured to store thedeclarative integration workflow such that the declarative integrationworkflow is able to be used to generate software code that, whenexecuted, performs the data exchange.
 31. The design workstation ofclaim 30 wherein the design module is further configured to generate auser interface used to design, a declarative integration workflow. 32.The design workstation of claim 30 wherein at least one predefinedintegration design pattern includes at least one of a pattern forvalidating a data collection for mandatory information, a pattern forsplitting data from one data collection into separate data collections,a pattern for invoking a key mapping function, a pattern for invoking adata transformation function, a pattern for invoking a connectivityfunction for a particular application system, and a pattern for invokinga connectivity function for invoking a particular service.
 33. Thedesign workstation of claim 30 wherein the design module is furtherconfigured to represent at least one integration design pattern thatdecomposes into at least two integration design patterns and from whicha user may select to be included in the declarative integrationworkflow.
 34. A computer-readable storage medium having embodied thereona computer program configured for use in the design of applicationintegration software that performs data exchange between at least twoapplication systems, the medium comprising: design code segmentconfigured to design, based on user input, a declarative integrationworkflow that includes predefined integration design patterns thatcollectively describe a data exchange between at least two applicationsystems, wherein: an integration design pattern identifies integrationfunctions used in the data exchange between at least two applicationsystems, an integration function identities a process used in datatransfers, and the at least two application systems each use a databasecapable of storing data related to business transactions andinstructions, that when executed, cause data related to the businesstransactions to be processed; a specifying code segment configured tospecify, based on user input, a sequence for performing the integrationdesign patterns to cause the data exchange; and a storage code segmentconfigured to store the declarative integration workflow such that thedeclarative integration workflow is able to be used to generate softwarecode that, when executed, performs the data exchange.
 35. Thecomputer-readable storage medium of claim 34 wherein the design codesegment is further configured to represent at least one integrationpattern that describes a function included in a particular data exchangebetween at least two application systems.
 36. The computer-readablestorage medium of claim 34 wherein the design code segment is furtherconfigured to represent at least one integration design pattern thatincludes at least one of a pattern for validating a data collection formandatory information, a pattern for splitting data from one datacollection into separate data collections, a pattern for invoking a keymapping function, a design pattern for invoking a data transformationfunction, a pattern the invoking a connectivity function for aparticular application system, and a pattern for invoking a connectivityfunction for invoking a particular service.
 37. The computer-readablemedium of claim 34 wherein the design code segment is further configuredto represent at least one of an integration design pattern thatdecomposes into at least two integration design patterns.
 38. Thecomputer-readable storage medium or signal of claim 34 furthercomprising a generative code segment configured to generate applicationintegration software based on the declarative integration workflow. 39.The computer-readable storage medium of claim 38 wherein the generativecode segment configured to generate a template for applicationintegration software.
 40. The computer-readable storage medium of claim38 wherein the generative code segment is configured to associate one ormore portions of the generated application integration software with oneor more portions of the declarative integration workflow, eachparticular portion of the generated application integration softwarebeing associated with a particular portion of the declarativeintegration workflow.
 41. The computer-readable storage medium of claim38 wherein the generative code segment is further configured to generateapplication integration software based on at least one layer ofapplication integration.
 42. The computer-readable storage medium ofclaim 41 wherein the generative code segment is further configured togenerate application integration software based on at least one of abusiness process layer, an integration design pattern layer, afunctional atom layer, a data transformation rule layer, a data and aphysical connection layer.
 43. The computer-readable storage medium ofclaim 42 wherein the functional atom layer comprises a functional atomlayer that identifies at least one functional atom that declarativelydescribes a discrete action that relates to an application integrationfunction.
 44. A method for use in the design of application integrationsoftware that performs data exchange between at least two applicationsystems comprising: designing, based on user input, a declarativeintegration workflow that includes predefined integration designpatterns that collectively describe a data exchange between at least twoapplication systems, wherein: an integration design pattern identifiesintegration functions used in the data exchange between at least twoapplication systems, an integration function identifies a process usedin data transfers, and the at least two application systems each use adatabase capable of storing data related to business transactions andinstructions that when executed, cause data related to the businesstransactions to be processed: specifying a sequence, based on userinput, for performing the integration design patterns to cause the dataexchange and storing the declarative integration workflow such that thedeclarative integration workflow is able to be used to generate softwarecode that, when executed, performs the data exchange.
 45. The method ofclaim 44 further comprising representing predefined integration patternsfrom which a user may select to be included in the declarativeintegration workflow.
 46. The method of claim 45 wherein representing atleast one integration pattern comprises representing at least oneintegration design pattern includes at least one of a pattern forvalidating a data collection for mandatory information, a pattern forsplitting data from one data collection into separate data collections,a pattern for invoking a key mapping function, a pattern for invoking adata transformation function, a pattern for invoking a connectivityfunction for a particular application system, and a integration designpattern for invoking a connectivity function for invoking a particularservice.
 47. The method of claim 45 wherein representing at least oneintegration pattern comprises representing at least one an integrationdesign pattern that decomposes into at least two integration designpatterns.
 48. The method of claim 44 further comprising generatingapplication integration software based on the declarative integrationworkflow.
 49. The method of claim 48 wherein generating applicationintegration software comprises generating a template for applicationintegration software.
 50. The method of claim 48 wherein associating thegenerated application integration software with the declarativeintegration workflow comprises associating at least one portion of thegenerated application integration software with at least one portion ofthe declarative integration workflow, each particular portion of thegenerated application integration software being associated with aparticular portion of the declarative integration workflow.
 51. Themethod of claim 48 wherein generating application integration softwarebased on the declarative integration workflow comprises generatingapplication integration software based on one or more layers ofapplication integration.
 52. The method of claim 51 wherein generatingapplication integration software based on at least one layer ofapplication integration comprises generating application integrationsoftware based on at least one of a business process layer, anintegration design pattern layer, a functional atom layer, a datatransformation rule layer, a data layer, and a physical connectionlayer.
 53. The method of claim 52 wherein the functional atom layercomprises a functional atom layer that identifies at least onefunctional atom that declaratively describes a discrete action thatrelates to an application integration function.